Skip to main content

Test Data & ConfigDirect link to Test Data & Config

Test Data & Config holds values your test cases reference instead of hardcoding — login credentials for a test account, sample search terms, addresses, or environment-specific configuration.

Why use it instead of hardcoding stepsDirect link to Why use it instead of hardcoding steps

A step like enter a destination becomes more reliable and reusable across environments when the actual value (Paris, New York, a QA account's email) is pulled from a shared data source rather than typed differently into every test case that needs it. It also means updating one value — say, rotating a test account's password — updates every test case that references it, instead of hunting through each one individually.

Managing entriesDirect link to Managing entries

  1. Go to Test Data & Config.
  2. Add a new entry with a key and value (for example qa_email → qa+cloudagents@yourcompany.com).
  3. Reference it from a test case step where you'd otherwise type a literal value.

ScopingDirect link to Scoping

Keep environment-specific values distinct where it matters — for example, separate login credentials for staging versus production — so a test case can be pointed at either environment without editing its steps.